Explanation of Change

Migrates native useSingleExecution off InteractionManager.runAfterInteractions onto a new heuristic helper, runAfterPredictedTransition, and fixes two TransitionTracker / ScreenLayout bugs that made that wait unreliable.

Bug fixes in transitionStart / transitionEnd tracking

1. Tab transitions were unreliable on Android for every tab, and on iOS for the Home tab specifically. Besides Home, the other bottom-tab routes host nested split navigators whose screens register via stack screenLayout, but that registration relies on transitionStart/transitionEnd, which react-native-screens only fires when tied to an actual view animation. Since tab switches use animation: 'none', no such animation ever runs on Android, so the nested-stack signal never fires there either, it just happened to look fine on iOS, where viewWillAppear fires on any visibility change regardless of animation. Home was simply the most visible case on any platform, since it has no nested navigator and thus no screenLayout wiring at all.
   Fixed by wiring bottomTabScreenLayoutWrapper directly into TabNavigator's own screenLayout, so tracking now comes from bottom-tabs' own transitionStart/transitionEnd, which fires consistently on both platforms regardless of the animation option.

2. Unmount can leave a stuck open transition. A screen may emit transitionStart and then unmount before transitionEnd; cleanup unsubscribes the listeners, so transitionEnd never arrives and queued callbacks wait up to MAX_TRANSITION_DURATION_MS (1s). Fixed by calling TransitionTracker.endTransition on unmount whenever a handle is still open.

runAfterPredictedTransition (prediction mechanism)
Naive TransitionTracker.runAfterTransitions() right after a press usually sees zero active transitions (registration gap) and unlocks too early. Always using waitForUpcomingTransition: true would make non-navigating presses wait up to 1s. The new helper predicts whether the current press will cause a visual transition by watching navigationRef __unsafe_action__ + state: if a navigable action is followed by a focused-route change within NAVIGATION_PREDICTION_WINDOW_MS (150ms), it waits for that upcoming transition to finish; otherwise it settles immediately. useSingleExecution then re-enables the button after the predicted (or already-active) transition ends - or right away when no transition is predicted.

Fixed Issues

$ #71913
$ #83071

Tests

Tests (on iOS and Android):

1. Go to Settings. You'll see a list of settings items.
2. As fast as you can, tap one of the list buttons, then immediately tap any other one.
3. Verify that no double navigation happens, only the first navigation that occurred goes through.

1. Create a workspace.
2. Go to the workspace, you'll see another list of buttons leading to different workspace pages.
3. Double-tap them the same way as above.
4. Verify that only the first navigation triggers and everything works as expected.

1. Go to any chat and send a message.
2. Start spamming reactions on that message: quickly add a reaction, reopen the reaction modal, add the next one, and repeat.
3. Verify that emojis are applied correctly, i.e. the reaction picker isn't left blocked when you reopen the modal.

1. Find any back button (top-left).
2. Double-tap that button.
3. Verify that only a single back navigation happens.

• Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

Same as tests.

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos